Skip to main content

Pre-Arm Checks

🔗 Pre-Arm Safety Checks – ArduPilot

List of possible messages.
MessageCauseSolution
3D Accel calibration neededAccelerometer calibration has not been doneComplete the accel calibration
Accels inconsistentTwo accelerometers are inconsistent by 0.75 m/s/sRe-do the accel calibration. Allow autopilot to warm-up and reboot. If failure continues replace autopilot
ADSB out of memoryAutopilot has run out of memoryDisable features or replace with a higher powered autopilot
Accels not healthyAt least one accelerometer is not providing dataReboot autopilot. If failure continues replace autopilot
AHRS: waiting for homeGPS has not gotten a fixIf indoors, go outside. Ensure compass and accelerometer calibrations have been completed. Eliminate radio-frequency sources that could interfere with the GPS
Battery below minimum arming capacityBattery capacity is below BATT_ARM_MAHReplace battery or adjust BATT_ARM_MAH
Battery below minimum arming voltageBattery voltage is below BATT_ARM_VOLTReplace battery or adjust BATT_ARM_VOLT
Battery capacity failsafe critical >= lowBattery failsafe misconfigurationCheck BATT_LOW_MAH is higher than BATT_CRT_MAH
Battery critical capacity failsafeBattery capacity is below BATT_CRT_MAHReplace battery or adjust BATT_CRT_MAH
Battery critical voltage failsafeBattery voltage is below BATT_CRT_VOLTReplace battery or adjust BATT_CRT_VOLT
Battery low capacity failsafeBattery capacity is below BATT_LOW_MAHReplace battery or adjust BATT_LOW_MAH
Battery low voltage failsafeBattery voltage is below BATT_LOW_VOLTReplace battery or adjust BATT_LOW_VOLT
Check mag field (xy diff:x>875)Compass horiz field strength is too large or smallRelocate vehicle away from metal in the environment. Move compass away from metal in the frame. repeat compass calibration. Disable internal compass.
Check mag field (z diff:x>875)Compass vert field strength is too large or smallRelocate vehicle away from metal in the environment. Move compass away from metal in the frame. repeat compass calibration. Disable internal compass.
Check mag field: x, max y, min zCompass field strength is too large or smallRelocate vehicle away from metal in the environment. Move compass away from metal in the frame. repeat compass calibration. Disable internal compass.
Compass not healthyAt least one compass is not providing dataCheck compass’s connection to autopilot and configuration
Compass offsets too highCompass offset params are too largeRelocate compass away from metal in the frame and repeat compass calibration. Disable internal compass. Increase COMPASS_OFFS_MAX.
Compasses inconsistentTwo compasses angles or field strength disagreeCheck compass orientations (e.g. COMPASS_ORIENT). Move compass away from metal in the frame. repeat compass calibration. Disable internal compass.
DroneCAN: Duplicate Node x../y!DroneCAN sees same node ids used by two devicesClear DroneCAN DNS server by setting CAN_D1_UC_OPTION = 1 and reboot
DroneCAN: Failed to access storage!Possible hardware issueReboot autopilot
DroneCAN: Failed to add Node x!DroneCAN could not init connection to a deviceCheck sensor’s physical connection and power supply
DroneCAN: Node x unhealthy!A DroneCAN device is not providing dataCheck sensor’s physical connection and power supply
Duplicate Aux Switch OptionsTwo auxiliary function switches for same featureCheck auxiliary function setup. Check for RCx_OPTION parameters with same values
EKF3 Roll/Pitch inconsistent by x degsoll or Pitch lean angle estimates are inconsistentNormally due to EKF3 not getting good enough GPS accuracy, but could be due to other sensors producing errors. Go outdoors, wait or reboot autopilot.
EKF3 waiting for GPS config dataautomatic GPS configuration has not completedCheck GPS connection and configuration especially if using DroneCAN GPS
EKF3 Yaw inconsistent by x degsYaw angle estimates are inconsistentWait or reboot autopilot
Failed to open mission.stgFailed to load mission from SD CardCheck SD card. Try to re-save mission to SD card
Failed to open mission.stgFailed to load mission from SD CardCheck SD card. Try to re-save mission to SD card
Fence requires positionIf fences are enabled, position estimate requiredWait or move vehicle to a location with a clear view of the sky. Reduce sources of radio-frequency interference
FENCE_ALT_MAX < FENCE_ALT_MINFENCE_ALT_MAX must be greater than FENCE_ALT_MINIncrease FENCE_ALT_MAX or lower FENCE_ALT_MIN
FENCE_MARGIN is less than FENCE_RADIUSFENCE_MARGIN must be larger than FENCE_RADIUSIncrease FENCE_RADIUS or reduce FENCE_MARGIN
FENCE_MARGIN too bigFENCE_ALT_MAX - FENCE_ALT_MIN < 2x FENCE_MARGINDecrease FENCE_MARGIN or increase difference between FENCE_ALT_MAX and FENCE_ALT_MIN
Fences enabled, but none selectedFences are enabled but none are definedDisable some or all fences using FENCE_ENABLE or FENCE_TYPE or define the missing fences
Fences invalidPolygon fence is invalidCheck polygon fence does not have overlapping lines
GPS and AHRS differ by XmGPS and EKF positions differ by at least 10mWait until GPS quality improves. Move vehicle to a location with a clear view of the sky. Reduce sources of radio-frequency interference
GPS blending unhealthyAt least one GPS is not providing good dataMove vehicle to a location with a clear view of the sky. Reduce sources of radio-frequency interference. Check GPS blending configuration
GPS Node x not set as instance yDroneCan GPS configuration errorCheck GPS1_CAN_NODEID and GPS2_CAN_NODEID
GPS positions differ by XmTwo GPSs reported positions differ by 50m or moreWait until GPS quality improves. Move vehicle to a location with a clear view of the sky. Reduce sources of radio-frequency interference
GPS x still configuring this GPSAutomatic GPS configuration has not completedWait until configuration completes. Check GPS connection and configuration especially if using DroneCAN GPS
GPS x: Bad fixGPS does not have a good lockMove vehicle to a location with a clear view of the sky. Reduce sources of radio-frequency interference
GPS x: not healthyGPS is not providing dataCheck GPSs physical connection to autopilot and configuration
GPS x: primary but TYPE 0Primary GPS has not been configuredCheck GPS_PRIMARY and confirm corresponding GPS1_TYPE or GPS2_TYPE matches type of GPS used
GPS x: was not foundGPS disconnected or incorrectly configuredCheck GPSs physical connection to autopilot and configuration
GPSx yaw not availableGPS-for-yaw configured but not workingMove to location with better GPS reception. Check GPS-for-yaw configuration
Gyros inconsistentTwo gyros are inconsistent by at least 5 deg/secReboot autopilot and hold vehicle still until gyro calibration completes. Allow autopilot to warm-up and reboot. If failure continues replace autopilot
Gyros not calibratedGyro calibration normally run at startup failedReboot autopilot and hold vehicle still until gyro calibration completes
Gyros not healthyAt least one gyro is not providing dataAt least one gyro is not providing data
heater temp lowBoard heater temp is below BRD_HEAT_TARGWait for board to heat up. Target temperature can be adjust using BRD_HEAT_TARG
Logging failedLogs could not be written. Maybe hardware failureReboot autopilot. Replace autopilot
Mount: check TYPEMount (aka camera gimbal) misconfigurationCheck MNT1_TYPE is valid. Check Gimbal configuration
Mount: not healthyMount is not communicating with autopilotCheck physical connection between autopilot and gimbal and check Gimbal configuration
OpenDroneID: ARM_STATUS not availableOpenDroneID misconfigurationsee Remote ID configuration
OpenDroneID: operator location must be setOperator location is not availablesee Remote ID configuration
RC not calibratedRC calibration has not been doneComplete the radio calibration. RC3_MIN and RC3_MAX must have been changed from their default values (1100 and 1900), and for channels 1 to 4, MIN value must be 1300 or less, and MAX value 1700 or more.
RC not foundRC failsafe enabled but no RC signalTurn on RC transmitter or check RC transmitters connection to autopilot. If operating with only a GCS, see Operation Using Only a Ground Control Station (GCS)
AHRS not healthy AHRS/EKF is not yet readyWait. Reboot autopilot
Altitude disparityBarometer and EKF altitudes differ by at least 1mWait for EKF altitude to stabilise. Reboot autopilot
Auto mode not armableVehicle cannot be armed in Auto modeSwitch to another mode (like Loiter) or set RTL_OPTIONS = 3. See Auto mode
Battery failsafeBattery failsafe has triggeredPlug in battery and check its voltage and capacity. See ref:battery failsafe configuration failsafe-battery
EKF attitude is badEKF does not have a good attitude estimateWait for EKF attitude to stabilize. Reboot autopilot. Replace autopilot
EKF compass varianceCompass direction appears incorrectRelocate vehicle away from metal in the environment. Move compass away from metal in the frame. repeat compass calibration. Disable internal compass.
EKF height varianceBarometer values are unstable or high vibrationWait. Measure vibration and add vibration isolation
EKF position varianceGPS position is unstableWait. If indoors, go outside. Eliminate radio-frequency sources that could interfere with the GPS
EKF velocity varianceGPS or optical flow velocities are unstableWait. If indoors, go outside. Eliminate radio-frequency sources that could interfere with the GPS. Check optical flow calibration
Fence enabled, need position estimateFence is enabled so need a position estimateWait. If indoors, go outside. Ensure compass and accelerometer calibrations have been completed. Eliminate radio-frequency sources that could interfere with the GPS. See Fence configuration
GCS failsafe onGCS failsafe has triggeredCheck telemetry connection. See ref:GCS Failsafe configuration gcs-failsafe
GPS glitchingGPS position is unstableWait. If indoors, go outside. Eliminate radio-frequency sources that could interfere with the GPS
High GPS HDOPGPS horizontal quality too lowWait or move to location with better GPS reception. You may raise GPS_HDOP_GOOD but this is rarely a good idea
Need Alt EstimateEKF has not yet calculated the altitude
Need Position EstimateEKF does not have a position estimateWait. If indoors, go outside. Ensure compass and accelerometer calibrations have been completed. Eliminate radio-frequency sources that could interfere with the GPS
Throttle below failsafeRC throttle input is below FS_THR_VALUETurn on RC transmitter or check FS_THR_VALUE. Check RC failsafe setup

Pre-arm Safety Checks which will prevent the vehicle from arming its propulsion system if any of a fairly large number of issues are discovered before movement including missed calibration, configuration or bad sensor data.

⚠️

These checks help prevent crashes or fly-aways when attempting to arm the motors, the autopilot performs a series of sensor status verifications.

If any of these checks fail:

  1. The autopilot will generate an error message.

  2. The message can be read in the messages section of either the Radio Control or Ground Control Station.

  3. The Drone will not arm the motors for safety reasons.

Operator Actions in Case of Error:

  1. Read the error message carefully.

  2. Identify the issue.

  3. Correct the issue before attempting to arm the motors again.